home *** CD-ROM | disk | FTP | other *** search
- Path: bubo.demon.co.uk!neil
- From: Neil Barrick <neil@bubo.demon.co.uk>
- Newsgroups: comp.dcom.modems,comp.os.ms-windows.win95.misc,comp.os.ms-windows.win95.setup
- Subject: Re: Modem hardware conflict? Please help me with this bizarre problem!
- Date: Sun, 10 Mar 1996 23:48:28 +0000
- Organization: British Steel
- Message-ID: <7028482396424ntc@bubo.demon.co.uk>
- References: <4gv4al$7u3@matahari.bae.bellcore.com> <4h9orv$aoe@minox.tripnet.se> <4hmh6k$9gu@sinsen.sn.no> <4hsppb$qfh@newnews.iafrica.com>
- Reply-To: neil@bubo.demon.co.uk
- NNTP-Posting-Host: bubo.demon.co.uk
- X-NNTP-Posting-Host: bubo.demon.co.uk
- X-Newsreader: NETcetera II - Registered Copy V2.21 (Registered) (c)1994-1995
-
- I've just tried to setup a Dial up network on my friends computer and
- suffered some strange problems, ie. in windows it just sits at the dial up
- script window and no text appears. Her setup is the same as
- mine (mine worked first time) except my modem is an external Trust V34 on
- COM1 and hers is an internal Trust V34 on COM4. She also has a Diamond
- Stealth 64 card whereas I have a Number 9. Her mouse is on COM1, mine is
- in the PS/2 socket. I've just joined this group and this is the first I've
- heard of the Diamond card causing modem problems, could someone
- please elaborate a bit as I've missed the previous threads, this sounds
- like it could be the answer to our problems. Any help is very gratefully
- recieved.
-
-
- In article <4hsppb$qfh@newnews.iafrica.com> Chris Quirke wrote :
- >> leifa@sn.no (Leif Arne Neset) wrote:
- >> >I've been troubled with the same combination of video, 486 and modem/serial
- >> >port. The problem is that the Diamond stealth card uses some internal
- >> >registers that have addresses that have the same last bits as the base
- >> >address of serial port com2. The problem is that the Diamond stealth driver
- >> >software writes information into registers of the UART of the
- >> >modem/serial port which then acts funny.
- >> Does your COM2: use COM4:'s IO port address? AFAIK the SVGA clash
- >> issue involves COM4:'s IO address, although as COM4: shares IRQ3 with
- >> COM2:, you may get some spill-over...
- >> >My solution was to strap my ISA serial card/modem as com1 and use
- >> >the built in VESA combo card com2 for the mouse.
- >> Me2; the beauty of mouse on COM2: is that you can add an internal
- >> modem on COM3:, or an external on COM1:, and not have to worry about
- >> IRQ clashes with the mouse, IO port clashes with S3 or misbehaviour
- >> due to a "missing" COM3: ;-)
- >>
-
-
-
-
-
- ----
- Neil
-
-